Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e05312d56c9150de3e6c2f563f83f9c5735f180162f5af7a3398c4440b132206

Tx prefix hash: b9ad68c7fec2094fc9940899cf09e22b8fbcf51b5f7903ae248fe4c0e30734e6
Tx public key: d6f6b8e06a0951d571c62d18c5481e496745bfdd6ed41ca5f6b611d7d33bedaa
Timestamp: 1733815933 Timestamp [UCT]: 2024-12-10 07:32:13 Age [y:d:h:m:s]: 00:028:11:33:08
Block: 1172004 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20352 RingCT/type: yes/0
Extra: 01d6f6b8e06a0951d571c62d18c5481e496745bfdd6ed41ca5f6b611d7d33bedaa021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8f7dca35ec9eb7d90cc22a5b29fa3457f5d1473bf4261360ba930bce68de6e0 0.600000000000 1657837 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": 1172014, "vin": [ { "gen": { "height": 1172004 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8f7dca35ec9eb7d90cc22a5b29fa3457f5d1473bf4261360ba930bce68de6e0" } } ], "extra": [ 1, 214, 246, 184, 224, 106, 9, 81, 213, 113, 198, 45, 24, 197, 72, 30, 73, 103, 69, 191, 221, 110, 212, 28, 165, 246, 182, 17, 215, 211, 59, 237, 170, 2, 17, 0, 0, 0, 4, 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