Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d295b46c48dd636285a632e3ecbc80055cafef7bf2e9048f0a5cbbd9a5c1c91

Tx prefix hash: b740ca294bc50fbfa7200cfec0806760b5c58305cd92a8ba9fadc1d9b42c078e
Tx public key: 363b811dc87cf9f821c211123ab3dc1e6c4c2775786944a4c43f4ff2d063c605
Timestamp: 1697402016 Timestamp [UCT]: 2023-10-15 20:33:36 Age [y:d:h:m:s]: 01:097:16:38:45
Block: 870417 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331017 RingCT/type: yes/0
Extra: 01363b811dc87cf9f821c211123ab3dc1e6c4c2775786944a4c43f4ff2d063c60502110000000375e3f0e9000000000000000000

1 output(s) for total of 0.801580564000 dcy

stealth address amount amount idx
00: ebd8a1253f1935e5f7935b7010bd217f5137df47c9506049d8aa3aaab88a8351 0.801580564000 1325296 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": 870427, "vin": [ { "gen": { "height": 870417 } } ], "vout": [ { "amount": 801580564, "target": { "key": "ebd8a1253f1935e5f7935b7010bd217f5137df47c9506049d8aa3aaab88a8351" } } ], "extra": [ 1, 54, 59, 129, 29, 200, 124, 249, 248, 33, 194, 17, 18, 58, 179, 220, 30, 108, 76, 39, 117, 120, 105, 68, 164, 196, 63, 79, 242, 208, 99, 198, 5, 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