Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59ccbd9510ce247b687ce79cd92c97922634c7dea2ecf4d2c09b19dcd54416d8

Tx prefix hash: 5c881418c2cfe53702bb717ea5532a619acc8cd377f63c0005f64ab926cf0ae4
Tx public key: cd1bce04b5c0530e5112fba396e4c762964e36f7f1cb10f7a6d6f81ff4a607b8
Timestamp: 1694265734 Timestamp [UCT]: 2023-09-09 13:22:14 Age [y:d:h:m:s]: 01:212:00:12:11
Block: 844387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 412620 RingCT/type: yes/0
Extra: 01cd1bce04b5c0530e5112fba396e4c762964e36f7f1cb10f7a6d6f81ff4a607b802110000000d33af99f4000000000000000000

1 output(s) for total of 0.977677031000 dcy

stealth address amount amount idx
00: 3f8939c5f4e2395d86d60747d6f8860c6210453089f33760076fcb88c0a89dc0 0.977677031000 1297691 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": 844397, "vin": [ { "gen": { "height": 844387 } } ], "vout": [ { "amount": 977677031, "target": { "key": "3f8939c5f4e2395d86d60747d6f8860c6210453089f33760076fcb88c0a89dc0" } } ], "extra": [ 1, 205, 27, 206, 4, 181, 192, 83, 14, 81, 18, 251, 163, 150, 228, 199, 98, 150, 78, 54, 247, 241, 203, 16, 247, 166, 214, 248, 31, 244, 166, 7, 184, 2, 17, 0, 0, 0, 13, 51, 175, 153, 244, 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