Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf54141e6ab63b1c025875e37a1ef93c3bab15cb00aca4f67f1f26817eda3896

Tx prefix hash: a6f2764388d1f203d5f23a1459e4c50870902a4bac50ec5d380f3e11878ff44e
Tx public key: 6154ee6822df7e6f919628a0b9a0a21ec4bd4553419db5970e53a0c13ee245ef
Timestamp: 1736017572 Timestamp [UCT]: 2025-01-04 19:06:12 Age [y:d:h:m:s]: 00:132:01:09:40
Block: 1190217 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94180 RingCT/type: yes/0
Extra: 016154ee6822df7e6f919628a0b9a0a21ec4bd4553419db5970e53a0c13ee245ef02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2db147f087345a503d5209db227a6a1bbb1e09daabeb479297f40c30172b3c39 0.600000000000 1676732 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": 1190227, "vin": [ { "gen": { "height": 1190217 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2db147f087345a503d5209db227a6a1bbb1e09daabeb479297f40c30172b3c39" } } ], "extra": [ 1, 97, 84, 238, 104, 34, 223, 126, 111, 145, 150, 40, 160, 185, 160, 162, 30, 196, 189, 69, 83, 65, 157, 181, 151, 14, 83, 160, 193, 62, 226, 69, 239, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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