Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c69b06dfc5c3c2b95d0f7966c17ff1240b2260e4a80c7d644be7af408119d8a1

Tx prefix hash: 868ed4df2fc199545ffa4b56baf0d34cc5ee98b056d385d3e42348520fb19e90
Tx public key: 5aa1102357e85c25280623841a35d29f1461bbc8bcaa3244e4ba31764cb69f5e
Timestamp: 1717547669 Timestamp [UCT]: 2024-06-05 00:34:29 Age [y:d:h:m:s]: 00:283:06:12:14
Block: 1037233 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202439 RingCT/type: yes/0
Extra: 015aa1102357e85c25280623841a35d29f1461bbc8bcaa3244e4ba31764cb69f5e0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6b6f0b65a91f80fb9621a540ce3772a6890f44f1f7c1f163a771dba4a6b4cc38 0.600000000000 1505764 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": 1037243, "vin": [ { "gen": { "height": 1037233 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6b6f0b65a91f80fb9621a540ce3772a6890f44f1f7c1f163a771dba4a6b4cc38" } } ], "extra": [ 1, 90, 161, 16, 35, 87, 232, 92, 37, 40, 6, 35, 132, 26, 53, 210, 159, 20, 97, 187, 200, 188, 170, 50, 68, 228, 186, 49, 118, 76, 182, 159, 94, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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