Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b460f338c063dbdc82441d0f1f38c65282a79398e8765842c82924c1a2fb5da7

Tx prefix hash: ede0982912b6dd22676e403f6b8882cf5a168035e3d4a83f3c4f9898fbd20518
Tx public key: 5fb20afcd8c03313c967df1b6f22500bf048c927e477e9fe8d0fed49820e0459
Timestamp: 1579788643 Timestamp [UCT]: 2020-01-23 14:10:43 Age [y:d:h:m:s]: 05:285:22:33:00
Block: 51136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1352927 RingCT/type: yes/0
Extra: 015fb20afcd8c03313c967df1b6f22500bf048c927e477e9fe8d0fed49820e0459021100000007bd0f9f9f000000000000000000

1 output(s) for total of 415.495223711000 dcy

stealth address amount amount idx
00: 34ee7d099b40f8d6e1191d1384c19d9e9e14c08c1ad267e9a17212aa1a754759 415.495223711000 94976 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": 51146, "vin": [ { "gen": { "height": 51136 } } ], "vout": [ { "amount": 415495223711, "target": { "key": "34ee7d099b40f8d6e1191d1384c19d9e9e14c08c1ad267e9a17212aa1a754759" } } ], "extra": [ 1, 95, 178, 10, 252, 216, 192, 51, 19, 201, 103, 223, 27, 111, 34, 80, 11, 240, 72, 201, 39, 228, 119, 233, 254, 141, 15, 237, 73, 130, 14, 4, 89, 2, 17, 0, 0, 0, 7, 189, 15, 159, 159, 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