Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d89abe454f77b566039373efebae8ef7fdd9be9bcdca97ecc0869e7e2b16824

Tx prefix hash: d6fdc673226458087e7a312f248a62f9435a4d2e0f5158d3a2ae2d69e7c22f6b
Tx public key: b0b891f208f54e18590bb7f091cbfb30f407848a8cbac50e06ed24204bce14d9
Timestamp: 1709767101 Timestamp [UCT]: 2024-03-06 23:18:21 Age [y:d:h:m:s]: 01:051:00:22:52
Block: 972725 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297471 RingCT/type: yes/0
Extra: 01b0b891f208f54e18590bb7f091cbfb30f407848a8cbac50e06ed24204bce14d902110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 287a9607ff4f619559639d0d086f5f88987b9ce584f50e634f8794701ed41a10 0.600000000000 1432644 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": 972735, "vin": [ { "gen": { "height": 972725 } } ], "vout": [ { "amount": 600000000, "target": { "key": "287a9607ff4f619559639d0d086f5f88987b9ce584f50e634f8794701ed41a10" } } ], "extra": [ 1, 176, 184, 145, 242, 8, 245, 78, 24, 89, 11, 183, 240, 145, 203, 251, 48, 244, 7, 132, 138, 140, 186, 197, 14, 6, 237, 36, 32, 75, 206, 20, 217, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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