Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4724e36c94ac2761c8a2eeb7ac3e11e17be0ff65545791497b4614d4e3138a6a

Tx prefix hash: 930805e515686cb8218406b50e1b46abd0833c138ff1f062d55f888a8b347351
Tx public key: 23b6749b36d363188c9e0cb5874f1b93b46d435bca4b70dd04c6db683b518cb5
Timestamp: 1713599849 Timestamp [UCT]: 2024-04-20 07:57:29 Age [y:d:h:m:s]: 01:193:16:54:37
Block: 1004476 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397114 RingCT/type: yes/0
Extra: 0123b6749b36d363188c9e0cb5874f1b93b46d435bca4b70dd04c6db683b518cb50211000000090011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b83f5e5d80a6de67a9f49ebd9bb4853662b7e871303e9abda5acf21e056744c 0.600000000000 1465044 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": 1004486, "vin": [ { "gen": { "height": 1004476 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b83f5e5d80a6de67a9f49ebd9bb4853662b7e871303e9abda5acf21e056744c" } } ], "extra": [ 1, 35, 182, 116, 155, 54, 211, 99, 24, 140, 158, 12, 181, 135, 79, 27, 147, 180, 109, 67, 91, 202, 75, 112, 221, 4, 198, 219, 104, 59, 81, 140, 181, 2, 17, 0, 0, 0, 9, 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