Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbbbd483da6f8783fb13e9d814920bf8863ce1b48939d86293f28bd8c2ee0510

Tx prefix hash: c48e636b805aa992baa3561b65fe0c28fca045fb2d4b0dd71cff52a1b71dcf14
Tx public key: 1c3f3ceef529ae9254e627686fbabb24559f3523dda78dca1861e6a44a8c32e1
Timestamp: 1738688723 Timestamp [UCT]: 2025-02-04 17:05:23 Age [y:d:h:m:s]: 00:289:21:59:20
Block: 1212056 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204964 RingCT/type: yes/0
Extra: 011c3f3ceef529ae9254e627686fbabb24559f3523dda78dca1861e6a44a8c32e1021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f50e75aa0c18400e1e981b7a8892841e901e82e34da92a5d150cb702cb2665a8 0.600000000000 1698823 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": 1212066, "vin": [ { "gen": { "height": 1212056 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f50e75aa0c18400e1e981b7a8892841e901e82e34da92a5d150cb702cb2665a8" } } ], "extra": [ 1, 28, 63, 60, 238, 245, 41, 174, 146, 84, 230, 39, 104, 111, 186, 187, 36, 85, 159, 53, 35, 221, 167, 141, 202, 24, 97, 230, 164, 74, 140, 50, 225, 2, 17, 0, 0, 0, 6, 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