Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05b13365b7a151b0f9fa5f30c598b06c9a5fe69698b9c9dd912393d0f1181296

Tx prefix hash: 756703ad81c55ce8dbaf20a66da6200c1facd33ed138691128a48202f0a48274
Tx public key: 8e3c7a3f4986c32ec37e14eb013b7b4358acc382b90f630108c52459bfbf4c5c
Timestamp: 1709123687 Timestamp [UCT]: 2024-02-28 12:34:47 Age [y:d:h:m:s]: 01:038:18:27:05
Block: 967392 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288711 RingCT/type: yes/0
Extra: 018e3c7a3f4986c32ec37e14eb013b7b4358acc382b90f630108c52459bfbf4c5c02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3bf9c29e1d239b16562d8c8d8fa6273785022023de42da5bdf8588b2ac80b68e 0.600000000000 1427169 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": 967402, "vin": [ { "gen": { "height": 967392 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3bf9c29e1d239b16562d8c8d8fa6273785022023de42da5bdf8588b2ac80b68e" } } ], "extra": [ 1, 142, 60, 122, 63, 73, 134, 195, 46, 195, 126, 20, 235, 1, 59, 123, 67, 88, 172, 195, 130, 185, 15, 99, 1, 8, 197, 36, 89, 191, 191, 76, 92, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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