Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2109b2f4b4e6f55d250e7df2af77fc31b14311dc52535126228f1e1897c27aac

Tx prefix hash: af579b9356dd35838d754e5ed14975ad81886297acece223a003982e4588c484
Tx public key: d4e2245e2ca38ba6d3d702fac3e59bcb5d507a077ae11c818ebf7c17e77d4809
Timestamp: 1707734899 Timestamp [UCT]: 2024-02-12 10:48:19 Age [y:d:h:m:s]: 00:208:15:52:54
Block: 955862 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149475 RingCT/type: yes/0
Extra: 01d4e2245e2ca38ba6d3d702fac3e59bcb5d507a077ae11c818ebf7c17e77d48090211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63ff8df6e9b6d6d899547b091e5501a6f0ae7e982c8e579941d216d11272d155 0.600000000000 1415162 of 15

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": 955872, "vin": [ { "gen": { "height": 955862 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63ff8df6e9b6d6d899547b091e5501a6f0ae7e982c8e579941d216d11272d155" } } ], "extra": [ 1, 212, 226, 36, 94, 44, 163, 139, 166, 211, 215, 2, 250, 195, 229, 155, 203, 93, 80, 122, 7, 122, 225, 28, 129, 142, 191, 124, 23, 231, 125, 72, 9, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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