Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40f1be4439a6f529bf1dead3c5d711a069d0a4a07c30665a5b2d2a9fdda43ea2

Tx prefix hash: 8d4f7b3ae95b7a3a079a2352547801371d30951203ec392c8145e6f04261724b
Tx public key: 6b4dbf1ca3680b1c1f37f53631e0c5bd3c9f18bccfba253aeb5f53a30580c637
Timestamp: 1725506188 Timestamp [UCT]: 2024-09-05 03:16:28 Age [y:d:h:m:s]: 00:208:16:17:51
Block: 1103204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148979 RingCT/type: yes/0
Extra: 016b4dbf1ca3680b1c1f37f53631e0c5bd3c9f18bccfba253aeb5f53a30580c63702110000000d91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1188a74e561541b0da7e0ba622d0fc5a3317f8a4e270a442be5eeb75ef399cc 0.600000000000 1579941 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": 1103214, "vin": [ { "gen": { "height": 1103204 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1188a74e561541b0da7e0ba622d0fc5a3317f8a4e270a442be5eeb75ef399cc" } } ], "extra": [ 1, 107, 77, 191, 28, 163, 104, 11, 28, 31, 55, 245, 54, 49, 224, 197, 189, 60, 159, 24, 188, 207, 186, 37, 58, 235, 95, 83, 163, 5, 128, 198, 55, 2, 17, 0, 0, 0, 13, 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