Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc73e6ca47bb14d60d4672ffd0b8af242a75695863094c4064e7734a369df14f

Tx prefix hash: 69d7e0155e9510bc621e96bc4f29455eec2b66ba23b68568e21f5dc719ff8f6b
Tx public key: 4dc802d316dab5572bee17a9617886469e65178cd7bd10fbb7c1527b4da76d5c
Timestamp: 1709673175 Timestamp [UCT]: 2024-03-05 21:12:55 Age [y:d:h:m:s]: 01:042:19:28:59
Block: 971952 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291587 RingCT/type: yes/0
Extra: 014dc802d316dab5572bee17a9617886469e65178cd7bd10fbb7c1527b4da76d5c0211000000140011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94ab73b73870044ef3a07fd7dcf3c89d5445f5bb0d541c6a3f224f9e6a190cc0 0.600000000000 1431857 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": 971962, "vin": [ { "gen": { "height": 971952 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94ab73b73870044ef3a07fd7dcf3c89d5445f5bb0d541c6a3f224f9e6a190cc0" } } ], "extra": [ 1, 77, 200, 2, 211, 22, 218, 181, 87, 43, 238, 23, 169, 97, 120, 134, 70, 158, 101, 23, 140, 215, 189, 16, 251, 183, 193, 82, 123, 77, 167, 109, 92, 2, 17, 0, 0, 0, 20, 0, 17, 5, 91, 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