Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 657f35b558de677de80da098f5eeb8b163aecb554450313e44265e237e3f855e

Tx prefix hash: ea8551d512bcc8fb489822cd422d5f34bff05d1f8f09c0118ba5b1ee80fdb9df
Tx public key: 73431a556b8475eaa8e6afa13053dbe689dd6fdb4fabb6e93f84043aacc7d543
Timestamp: 1700268306 Timestamp [UCT]: 2023-11-18 00:45:06 Age [y:d:h:m:s]: 01:357:03:32:08
Block: 893971 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 514142 RingCT/type: yes/0
Extra: 0173431a556b8475eaa8e6afa13053dbe689dd6fdb4fabb6e93f84043aacc7d54302110000000175e3f0e9000000000000000000

1 output(s) for total of 0.669734952000 dcy

stealth address amount amount idx
00: 907bfd399f08ff644746565a3185aae0858af008d6a5b165afef94d6b879730c 0.669734952000 1350158 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": 893981, "vin": [ { "gen": { "height": 893971 } } ], "vout": [ { "amount": 669734952, "target": { "key": "907bfd399f08ff644746565a3185aae0858af008d6a5b165afef94d6b879730c" } } ], "extra": [ 1, 115, 67, 26, 85, 107, 132, 117, 234, 168, 230, 175, 161, 48, 83, 219, 230, 137, 221, 111, 219, 79, 171, 182, 233, 63, 132, 4, 58, 172, 199, 213, 67, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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