Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd7e1bbd995227146e570fa8b00cdd265feceac5f47410a7309508d05d8820cd

Tx prefix hash: 0cd4d453b5f709f70a972f71979a2415574ffd4d0fbe97064346be058b1f1319
Tx public key: cbdc89f9900ec66b315b4c206d813218cc1f3afca8e0154a4f667a12ba1b909e
Timestamp: 1737273560 Timestamp [UCT]: 2025-01-19 07:59:20 Age [y:d:h:m:s]: 00:150:04:37:27
Block: 1200575 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107084 RingCT/type: yes/0
Extra: 01cbdc89f9900ec66b315b4c206d813218cc1f3afca8e0154a4f667a12ba1b909e02110000000b007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 29081706b6b4db21ff0db44d3a61ff2fe2c1b491f8d4bb1370b7fbacd624dc21 0.600000000000 1687220 of 15

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": 1200585, "vin": [ { "gen": { "height": 1200575 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29081706b6b4db21ff0db44d3a61ff2fe2c1b491f8d4bb1370b7fbacd624dc21" } } ], "extra": [ 1, 203, 220, 137, 249, 144, 14, 198, 107, 49, 91, 76, 32, 109, 129, 50, 24, 204, 31, 58, 252, 168, 224, 21, 74, 79, 102, 122, 18, 186, 27, 144, 158, 2, 17, 0, 0, 0, 11, 0, 127, 151, 138, 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