Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52d0c26f4d683c56eec8d2e50e1fd37f4c6b94ec27f6d5cf4dadad7e34b0562d

Tx prefix hash: d391dc4026f19d72ed5270f3dd616f6942e749c88b37e143249ab80d3e6059f3
Tx public key: 26d363a7a5f118ff7bf71fb011b3cbbd94dd7a0f8184b10e9e1ecfbe07fbb93b
Timestamp: 1698501374 Timestamp [UCT]: 2023-10-28 13:56:14 Age [y:d:h:m:s]: 02:009:10:50:40
Block: 879539 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 526315 RingCT/type: yes/0
Extra: 0126d363a7a5f118ff7bf71fb011b3cbbd94dd7a0f8184b10e9e1ecfbe07fbb93b02110000000b33af99f4000000000000000000

1 output(s) for total of 0.747691068000 dcy

stealth address amount amount idx
00: 14d2925cba8149c2454bbdc4dc98b2a0798975eff1687a8d8c515265ddf6645a 0.747691068000 1335067 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": 879549, "vin": [ { "gen": { "height": 879539 } } ], "vout": [ { "amount": 747691068, "target": { "key": "14d2925cba8149c2454bbdc4dc98b2a0798975eff1687a8d8c515265ddf6645a" } } ], "extra": [ 1, 38, 211, 99, 167, 165, 241, 24, 255, 123, 247, 31, 176, 17, 179, 203, 189, 148, 221, 122, 15, 129, 132, 177, 14, 158, 30, 207, 190, 7, 251, 185, 59, 2, 17, 0, 0, 0, 11, 51, 175, 153, 244, 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