Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a841313a9ea74cf1d837e3b6e9b6738345aaf74ff0f45395667a6e08c25003d6

Tx prefix hash: 9f498c810a354d34d7d40bcf6434f92765b220eecdc299f90711b88e1f33bbd4
Tx public key: 887a5bf9e9d2250aebeee7688fae4d5c955c935a7962f691196b60bbafa527db
Timestamp: 1693147110 Timestamp [UCT]: 2023-08-27 14:38:30 Age [y:d:h:m:s]: 02:098:15:52:29
Block: 835111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 590260 RingCT/type: yes/0
Extra: 01887a5bf9e9d2250aebeee7688fae4d5c955c935a7962f691196b60bbafa527db021100000001faf35c9c000000000000000000

1 output(s) for total of 1.049374881000 dcy

stealth address amount amount idx
00: d3195608b554a19ab3bf125ea8bc4d566b8b3cd57b32e17265a9990acde36855 1.049374881000 1287649 of 0

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": 835121, "vin": [ { "gen": { "height": 835111 } } ], "vout": [ { "amount": 1049374881, "target": { "key": "d3195608b554a19ab3bf125ea8bc4d566b8b3cd57b32e17265a9990acde36855" } } ], "extra": [ 1, 136, 122, 91, 249, 233, 210, 37, 10, 235, 238, 231, 104, 143, 174, 77, 92, 149, 92, 147, 90, 121, 98, 246, 145, 25, 107, 96, 187, 175, 165, 39, 219, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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