Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c177739fee441f84c473a35f6c4c8cf35af9e8c3564aec1849e1b853eb279093

Tx prefix hash: 37aae5309809419b744bd5887c9845af120dd22a392e4eebafd5d561110ce617
Tx public key: b7e6c14cd8da96afbcefd4b1b7b92b8f1c45016a9adac89228a4eaf55c8f9fa0
Timestamp: 1728437852 Timestamp [UCT]: 2024-10-09 01:37:32 Age [y:d:h:m:s]: 00:156:05:34:06
Block: 1127505 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111452 RingCT/type: yes/0
Extra: 01b7e6c14cd8da96afbcefd4b1b7b92b8f1c45016a9adac89228a4eaf55c8f9fa002110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7873bb3382739265ea33acf4545bd5a6d15e0ec3d1bfa8b662d77010718121dc 0.600000000000 1610312 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": 1127515, "vin": [ { "gen": { "height": 1127505 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7873bb3382739265ea33acf4545bd5a6d15e0ec3d1bfa8b662d77010718121dc" } } ], "extra": [ 1, 183, 230, 193, 76, 216, 218, 150, 175, 188, 239, 212, 177, 183, 185, 43, 143, 28, 69, 1, 106, 154, 218, 200, 146, 40, 164, 234, 245, 92, 143, 159, 160, 2, 17, 0, 0, 0, 4, 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