Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd668b7ae1e4c8b952976a54ba118656a8bbe5aeb24131904f587718fbee36a6

Tx prefix hash: a7b2507191a6acd48906d144d48c0aeb68e65cf61bc448a25793a24587c90809
Tx public key: 6121e825b7c07e2b9916d675f72bd1b7df537626049af7b92e36e8e7d234d76d
Timestamp: 1577740718 Timestamp [UCT]: 2019-12-30 21:18:38 Age [y:d:h:m:s]: 04:364:23:07:54
Block: 35331 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1149909 RingCT/type: yes/0
Extra: 016121e825b7c07e2b9916d675f72bd1b7df537626049af7b92e36e8e7d234d76d02110000009d398c17aa000000000000000000

1 output(s) for total of 468.742772971000 dcy

stealth address amount amount idx
00: d3338c0dab4ab5efdd266bd5691d3b1e22a25a1a8e92cc0dc279c257690c9ee3 468.742772971000 59513 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": 35341, "vin": [ { "gen": { "height": 35331 } } ], "vout": [ { "amount": 468742772971, "target": { "key": "d3338c0dab4ab5efdd266bd5691d3b1e22a25a1a8e92cc0dc279c257690c9ee3" } } ], "extra": [ 1, 97, 33, 232, 37, 183, 192, 126, 43, 153, 22, 214, 117, 247, 43, 209, 183, 223, 83, 118, 38, 4, 154, 247, 185, 46, 54, 232, 231, 210, 52, 215, 109, 2, 17, 0, 0, 0, 157, 57, 140, 23, 170, 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