Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea2d80738063a8a3e95efa11428afa3cd23444ddc5577f9e17aaa09595defb02

Tx prefix hash: 8fccee51b7747d552ecbf9b3f3a33d6a7ec06cc62348e0e9e5bbba089f57a013
Tx public key: d273cfcdbb2e8a374f796083a0302dfcff9412981b7eb7af1fdcd4ef9a356019
Timestamp: 1716032116 Timestamp [UCT]: 2024-05-18 11:35:16 Age [y:d:h:m:s]: 01:174:06:40:12
Block: 1024665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 383158 RingCT/type: yes/0
Extra: 01d273cfcdbb2e8a374f796083a0302dfcff9412981b7eb7af1fdcd4ef9a35601902110000000659dad3f5000000000000000000

1 output(s) for total of 0.615610000000 dcy

stealth address amount amount idx
00: 64887af5139f10d9193d000e8a9b23c00e4c8ccc60ae4c8437e7a7c13389902f 0.615610000000 1490584 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": 1024675, "vin": [ { "gen": { "height": 1024665 } } ], "vout": [ { "amount": 615610000, "target": { "key": "64887af5139f10d9193d000e8a9b23c00e4c8ccc60ae4c8437e7a7c13389902f" } } ], "extra": [ 1, 210, 115, 207, 205, 187, 46, 138, 55, 79, 121, 96, 131, 160, 48, 45, 252, 255, 148, 18, 152, 27, 126, 183, 175, 31, 220, 212, 239, 154, 53, 96, 25, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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