Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4182232dcc19e497673a7a5bb002fc8def4e6065a292e9c0205001eec0eb92e

Tx prefix hash: 633bb1abfa05a89c62340227cc83042a2378712c943ce3f458167272c55fcc75
Tx public key: 5c1bbefb0dc8931d0d93d6b4858e633d2aa12a84d40dbc3558f9b6063d83d256
Timestamp: 1718723040 Timestamp [UCT]: 2024-06-18 15:04:00 Age [y:d:h:m:s]: 00:278:09:33:13
Block: 1046966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198927 RingCT/type: yes/0
Extra: 015c1bbefb0dc8931d0d93d6b4858e633d2aa12a84d40dbc3558f9b6063d83d25602110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7cc2186c20459f44a910543c1b8a16588daaeac09b6a67f2f45a532f52f7d389 0.600000000000 1516785 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": 1046976, "vin": [ { "gen": { "height": 1046966 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7cc2186c20459f44a910543c1b8a16588daaeac09b6a67f2f45a532f52f7d389" } } ], "extra": [ 1, 92, 27, 190, 251, 13, 200, 147, 29, 13, 147, 214, 180, 133, 142, 99, 61, 42, 161, 42, 132, 212, 13, 188, 53, 88, 249, 182, 6, 61, 131, 210, 86, 2, 17, 0, 0, 0, 3, 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