Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: acda23f3487df1fd994579b8862b84d12cd68a8236ac6c229c000175a3e59b54

Tx prefix hash: f0717861c13e76b143e67c1adbb6eaaf7d8bb5e88b84c8262bbde2a514a029bc
Tx public key: 45f57f77918ee5e1055d8308e7bfd81e72b560257bb7a9d46516c916b2a030d2
Timestamp: 1720099831 Timestamp [UCT]: 2024-07-04 13:30:31 Age [y:d:h:m:s]: 00:204:11:11:46
Block: 1058378 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146273 RingCT/type: yes/0
Extra: 0145f57f77918ee5e1055d8308e7bfd81e72b560257bb7a9d46516c916b2a030d20211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c7d36f2b922758fc5b10dee7a0f4246c81abfe62561e73e7e2a6de664e3b675 0.600000000000 1528831 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": 1058388, "vin": [ { "gen": { "height": 1058378 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c7d36f2b922758fc5b10dee7a0f4246c81abfe62561e73e7e2a6de664e3b675" } } ], "extra": [ 1, 69, 245, 127, 119, 145, 142, 229, 225, 5, 93, 131, 8, 231, 191, 216, 30, 114, 181, 96, 37, 123, 183, 169, 212, 101, 22, 201, 22, 178, 160, 48, 210, 2, 17, 0, 0, 0, 6, 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