Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac6f312807ddb0518cbec403c6ab06074e9f8b449a96c3a6835fb6785ce4454e

Tx prefix hash: 14457c4984f36e5e938a4fe04314c5a220f8363f783c037a1953a0f26e457df3
Tx public key: 199c37cc85d68422b8e02db55d415a8be6e71ee2deff4c3fbdd6b4d94e9b0295
Timestamp: 1735396949 Timestamp [UCT]: 2024-12-28 14:42:29 Age [y:d:h:m:s]: 00:084:23:34:13
Block: 1185064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60539 RingCT/type: yes/0
Extra: 01199c37cc85d68422b8e02db55d415a8be6e71ee2deff4c3fbdd6b4d94e9b02950211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5bbe6276630636bc82ec50336002ef44ca1ee28074f1fdb52d62a727c0a2b229 0.600000000000 1671529 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": 1185074, "vin": [ { "gen": { "height": 1185064 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5bbe6276630636bc82ec50336002ef44ca1ee28074f1fdb52d62a727c0a2b229" } } ], "extra": [ 1, 25, 156, 55, 204, 133, 214, 132, 34, 184, 224, 45, 181, 93, 65, 90, 139, 230, 231, 30, 226, 222, 255, 76, 63, 189, 214, 180, 217, 78, 155, 2, 149, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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