Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 019649a9f964a9ee4ce0bebb3161d7939be4f117d1ba17bf9764ee46d4c8556e

Tx prefix hash: 11f0d5ae1022c7e11b8cc5b7559cd6f65a6d9b561eb321b082e9d4ee15cbe369
Tx public key: bddfec662f86a0a08caea02e533826d8eb4504ae6c2e0f704cfe1f6d80c3c283
Timestamp: 1700486664 Timestamp [UCT]: 2023-11-20 13:24:24 Age [y:d:h:m:s]: 01:060:19:07:37
Block: 895772 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304822 RingCT/type: yes/0
Extra: 01bddfec662f86a0a08caea02e533826d8eb4504ae6c2e0f704cfe1f6d80c3c28302110000000375e3f0e9000000000000000000

1 output(s) for total of 0.660595333000 dcy

stealth address amount amount idx
00: 21359f3f47f8e4a69edad6293155ca467bfa16310ea10787fd1f79b6c87a2529 0.660595333000 1352019 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": 895782, "vin": [ { "gen": { "height": 895772 } } ], "vout": [ { "amount": 660595333, "target": { "key": "21359f3f47f8e4a69edad6293155ca467bfa16310ea10787fd1f79b6c87a2529" } } ], "extra": [ 1, 189, 223, 236, 102, 47, 134, 160, 160, 140, 174, 160, 46, 83, 56, 38, 216, 235, 69, 4, 174, 108, 46, 15, 112, 76, 254, 31, 109, 128, 195, 194, 131, 2, 17, 0, 0, 0, 3, 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