Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b97d61dfb03db6bf172037d8701a18925c8452454ecdfae924803bd6e9345946

Tx prefix hash: 17c98bba7c3017a4a2d106c1736ecfc2629463c5d5894aacd2a6bdcd39b548b2
Tx public key: b434c8c301e514a1f02833dcfe07166a880fd6aaafdebac475bf900154a16c7c
Timestamp: 1625634557 Timestamp [UCT]: 2021-07-07 05:09:17 Age [y:d:h:m:s]: 03:173:17:19:43
Block: 289494 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 894378 RingCT/type: yes/0
Extra: 01b434c8c301e514a1f02833dcfe07166a880fd6aaafdebac475bf900154a16c7c02110000002fd142c209000000000000000000

1 output(s) for total of 67.419683470000 dcy

stealth address amount amount idx
00: 3e1f667f293e2dd85ba804f00d9deb74d196a666ae350db7a48ed184e587c48f 67.419683470000 606334 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": 289504, "vin": [ { "gen": { "height": 289494 } } ], "vout": [ { "amount": 67419683470, "target": { "key": "3e1f667f293e2dd85ba804f00d9deb74d196a666ae350db7a48ed184e587c48f" } } ], "extra": [ 1, 180, 52, 200, 195, 1, 229, 20, 161, 240, 40, 51, 220, 254, 7, 22, 106, 136, 15, 214, 170, 175, 222, 186, 196, 117, 191, 144, 1, 84, 161, 108, 124, 2, 17, 0, 0, 0, 47, 209, 66, 194, 9, 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