Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23f36bfc496a5f1cd91378b513747ed7340be111dd0c081d4ccf2fdde30e1487

Tx prefix hash: a681ea4d0609158239f8fbdcfbab43a0fa762e78d2c6bda59eafd0a6abea3b53
Tx public key: f3b90b512379a1be7f4fbec0a3cbde5d3fecc4d195026e86fee420bd86f3ed6e
Timestamp: 1729219963 Timestamp [UCT]: 2024-10-18 02:52:43 Age [y:d:h:m:s]: 00:192:12:15:38
Block: 1133999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137378 RingCT/type: yes/0
Extra: 01f3b90b512379a1be7f4fbec0a3cbde5d3fecc4d195026e86fee420bd86f3ed6e0211000000023cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 384fc3111b6e32652e134723c0369598ea0eb9e010511043c989e7a85df03173 0.600000000000 1617232 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": 1134009, "vin": [ { "gen": { "height": 1133999 } } ], "vout": [ { "amount": 600000000, "target": { "key": "384fc3111b6e32652e134723c0369598ea0eb9e010511043c989e7a85df03173" } } ], "extra": [ 1, 243, 185, 11, 81, 35, 121, 161, 190, 127, 79, 190, 192, 163, 203, 222, 93, 63, 236, 196, 209, 149, 2, 110, 134, 254, 228, 32, 189, 134, 243, 237, 110, 2, 17, 0, 0, 0, 2, 60, 208, 252, 6, 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