Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e473045e6edf30ce8c1290b9eeb67951f4c8b583f6d5e6ee6f68dd2b237d88d0

Tx prefix hash: d207d501606702819c5df86c8a324bc2e5f13303a100089ad41501cac2a2142b
Tx public key: 2f625c9e3d16a078fbba8a8db51155f308823383bfff750baeb9e5a52abf1a9a
Timestamp: 1698314951 Timestamp [UCT]: 2023-10-26 10:09:11 Age [y:d:h:m:s]: 01:087:15:14:39
Block: 877999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323808 RingCT/type: yes/0
Extra: 012f625c9e3d16a078fbba8a8db51155f308823383bfff750baeb9e5a52abf1a9a0211000000034b8f5122000000000000000000

1 output(s) for total of 0.756527734000 dcy

stealth address amount amount idx
00: b5c2256e3f25afe42ba51a78d29e81d1724d2cf21ea5879b32713afc9764046a 0.756527734000 1333403 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": 878009, "vin": [ { "gen": { "height": 877999 } } ], "vout": [ { "amount": 756527734, "target": { "key": "b5c2256e3f25afe42ba51a78d29e81d1724d2cf21ea5879b32713afc9764046a" } } ], "extra": [ 1, 47, 98, 92, 158, 61, 22, 160, 120, 251, 186, 138, 141, 181, 17, 85, 243, 8, 130, 51, 131, 191, 255, 117, 11, 174, 185, 229, 165, 42, 191, 26, 154, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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