Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afa97a2941b1c5dbbd103a4a0949a31ddb728fb40ead401f6ca45324c47c60ac

Tx prefix hash: 25735cc811a67082365bb033df783dc453be16df01db5dbb8ad3197e67e5237a
Tx public key: b3e8680ec7ea3a4da9b8e8f6193c6279a00b25e8ed9f2658c90f36a713dc04ff
Timestamp: 1647890710 Timestamp [UCT]: 2022-03-21 19:25:10 Age [y:d:h:m:s]: 02:294:07:15:54
Block: 463437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 729870 RingCT/type: yes/0
Extra: 01b3e8680ec7ea3a4da9b8e8f6193c6279a00b25e8ed9f2658c90f36a713dc04ff0211000000015eb576c5000000000000000000

1 output(s) for total of 17.883029634000 dcy

stealth address amount amount idx
00: a2ead4564b86209980e048d45fde24ed3504e6dc044f1c66e57803ccdfd06f32 17.883029634000 881106 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": 463447, "vin": [ { "gen": { "height": 463437 } } ], "vout": [ { "amount": 17883029634, "target": { "key": "a2ead4564b86209980e048d45fde24ed3504e6dc044f1c66e57803ccdfd06f32" } } ], "extra": [ 1, 179, 232, 104, 14, 199, 234, 58, 77, 169, 184, 232, 246, 25, 60, 98, 121, 160, 11, 37, 232, 237, 159, 38, 88, 201, 15, 54, 167, 19, 220, 4, 255, 2, 17, 0, 0, 0, 1, 94, 181, 118, 197, 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