Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d74c63d21474bff432ac6e76eeb071f8a3507c2045c19f1fb76991a24dedb94

Tx prefix hash: bcfa15d00034f7e474ca10dddd20164e81d3da44e67bbfb9ba1c091511c26777
Tx public key: bfc124ee70cc51f7410d0edf4925b96871260d8123ea46ad4a39b1507550e9a7
Timestamp: 1723052639 Timestamp [UCT]: 2024-08-07 17:43:59 Age [y:d:h:m:s]: 01:091:11:10:12
Block: 1082855 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323846 RingCT/type: yes/0
Extra: 01bfc124ee70cc51f7410d0edf4925b96871260d8123ea46ad4a39b1507550e9a702110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d498bdf909a5a2f3569039f0155215d7c8d9e1d6e88e46bc5df7c0d6230e26b4 0.600000000000 1556690 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": 1082865, "vin": [ { "gen": { "height": 1082855 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d498bdf909a5a2f3569039f0155215d7c8d9e1d6e88e46bc5df7c0d6230e26b4" } } ], "extra": [ 1, 191, 193, 36, 238, 112, 204, 81, 247, 65, 13, 14, 223, 73, 37, 185, 104, 113, 38, 13, 129, 35, 234, 70, 173, 74, 57, 177, 80, 117, 80, 233, 167, 2, 17, 0, 0, 0, 2, 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