Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08ebb97bf78d5f2cf3c5ab660c3df64db0b69b20ddaa15abf02e790b8240017d

Tx prefix hash: 3644f5fc0c28c067b48b5f9f115902b727f07af6befa4f90282d87c090bc19e2
Tx public key: cdf8c513953c064875e00fd97ff5f7362eb1e4c782341db111388014f63d4c6b
Timestamp: 1725764192 Timestamp [UCT]: 2024-09-08 02:56:32 Age [y:d:h:m:s]: 00:235:19:13:11
Block: 1105348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168375 RingCT/type: yes/0
Extra: 01cdf8c513953c064875e00fd97ff5f7362eb1e4c782341db111388014f63d4c6b02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d0bf82b0c2a4cfacb42247f0e5ffb753aa0074834dbdcd7cf8963966940fce5 0.600000000000 1582689 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": 1105358, "vin": [ { "gen": { "height": 1105348 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d0bf82b0c2a4cfacb42247f0e5ffb753aa0074834dbdcd7cf8963966940fce5" } } ], "extra": [ 1, 205, 248, 197, 19, 149, 60, 6, 72, 117, 224, 15, 217, 127, 245, 247, 54, 46, 177, 228, 199, 130, 52, 29, 177, 17, 56, 128, 20, 246, 61, 76, 107, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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