Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c96ddad6938fec4a792e156c2f3650a53e4ce7745569efd1a05cf3ec2244617b

Tx prefix hash: a8f77583df75ea8bf423f1719c668db66ff86aebd1fd7c8eb42d9cf59b9269ff
Tx public key: bdee1ee5dd4c0d271d7b9bc06f913c8fa0158136fea1d93ee08bfa0a3c9d744a
Timestamp: 1699766929 Timestamp [UCT]: 2023-11-12 05:28:49 Age [y:d:h:m:s]: 01:004:03:04:18
Block: 889821 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264304 RingCT/type: yes/0
Extra: 01bdee1ee5dd4c0d271d7b9bc06f913c8fa0158136fea1d93ee08bfa0a3c9d744a02110000000274c3735f000000000000000000

1 output(s) for total of 0.691279444000 dcy

stealth address amount amount idx
00: 05ff75b00d7e10b82db541e8d01efa9ac522547049ba8a2e8642c02659e0aed6 0.691279444000 1345838 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": 889831, "vin": [ { "gen": { "height": 889821 } } ], "vout": [ { "amount": 691279444, "target": { "key": "05ff75b00d7e10b82db541e8d01efa9ac522547049ba8a2e8642c02659e0aed6" } } ], "extra": [ 1, 189, 238, 30, 229, 221, 76, 13, 39, 29, 123, 155, 192, 111, 145, 60, 143, 160, 21, 129, 54, 254, 161, 217, 62, 224, 139, 250, 10, 60, 157, 116, 74, 2, 17, 0, 0, 0, 2, 116, 195, 115, 95, 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