Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: fcd5db0beb0ed7ace9bb326b96845e800444c66e44bacda4f6ad14826727af6f

Tx prefix hash: fea0a4c538a3358bfd4b42ec50fa4232a536776a698f01a5d98c24e4b4eed5a3
Tx public key: ec607b52c1cfe1f8ca7fb8043b636b71a703af9443a43c6fed39edd95c0496ea
Timestamp: 1681121797 Timestamp [UCT]: 2023-04-10 10:16:37 Age [y:d:h:m:s]: 01:308:17:11:48
Block: 735479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 481911 RingCT/type: yes/0
Extra: 01ec607b52c1cfe1f8ca7fb8043b636b71a703af9443a43c6fed39edd95c0496ea02110000000375e3f0e9000000000000000000

1 output(s) for total of 2.244155703000 dcy

stealth address amount amount idx
00: 6911fa229fd5e33ed2a630a7e0273ab9c24267a2aff39e058182198ddcce422a 2.244155703000 1181808 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 735489, "vin": [ { "gen": { "height": 735479 } } ], "vout": [ { "amount": 2244155703, "target": { "key": "6911fa229fd5e33ed2a630a7e0273ab9c24267a2aff39e058182198ddcce422a" } } ], "extra": [ 1, 236, 96, 123, 82, 193, 207, 225, 248, 202, 127, 184, 4, 59, 99, 107, 113, 167, 3, 175, 148, 67, 164, 60, 111, 237, 57, 237, 217, 92, 4, 150, 234, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8