Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d3d8489e54d25916f008a61cddf9ed8e561667e5e7ffce32cb54575081e21ce

Tx prefix hash: b8e73a168e227bada5b45ffb45d2bf42283e0ae783ccdfb519fd6fb96746d966
Tx public key: dcab2b888d73c352d097d3182f12a93e46f956d2b74f664dbd32bbf6f14047c9
Timestamp: 1579204912 Timestamp [UCT]: 2020-01-16 20:01:52 Age [y:d:h:m:s]: 04:352:21:39:20
Block: 47067 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1141675 RingCT/type: yes/0
Extra: 01dcab2b888d73c352d097d3182f12a93e46f956d2b74f664dbd32bbf6f14047c90211000000012264afe6000000000000000000

1 output(s) for total of 428.605491485000 dcy

stealth address amount amount idx
00: 0edeb0c234dd4c6cbd7f3c1e11b76d47652ab2caaa389c37a949759e1f26a530 428.605491485000 86920 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": 47077, "vin": [ { "gen": { "height": 47067 } } ], "vout": [ { "amount": 428605491485, "target": { "key": "0edeb0c234dd4c6cbd7f3c1e11b76d47652ab2caaa389c37a949759e1f26a530" } } ], "extra": [ 1, 220, 171, 43, 136, 141, 115, 195, 82, 208, 151, 211, 24, 47, 18, 169, 62, 70, 249, 86, 210, 183, 79, 102, 77, 189, 50, 187, 246, 241, 64, 71, 201, 2, 17, 0, 0, 0, 1, 34, 100, 175, 230, 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