Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f329eba20b489b40aac50e381727ba513fce2c67cd9b322fc4e8ee7f64ed433

Tx prefix hash: 0d3e8404b674fd7199068a1a4b5a8c55f5c6851a99e648727096e08de639a6b5
Tx public key: 163163bdcfdac08055045dd7a3ebbf41123168c80ffe8d444b4f1412fa15e9b5
Timestamp: 1705346614 Timestamp [UCT]: 2024-01-15 19:23:34 Age [y:d:h:m:s]: 01:300:02:09:30
Block: 936051 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 473299 RingCT/type: yes/0
Extra: 01163163bdcfdac08055045dd7a3ebbf41123168c80ffe8d444b4f1412fa15e9b502110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f420ec84b4ae269de4d145e2e3af087158d4fa0bc9ee571f8f0792b6b3f0aa65 0.600000000000 1394073 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": 936061, "vin": [ { "gen": { "height": 936051 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f420ec84b4ae269de4d145e2e3af087158d4fa0bc9ee571f8f0792b6b3f0aa65" } } ], "extra": [ 1, 22, 49, 99, 189, 207, 218, 192, 128, 85, 4, 93, 215, 163, 235, 191, 65, 18, 49, 104, 200, 15, 254, 141, 68, 75, 79, 20, 18, 250, 21, 233, 181, 2, 17, 0, 0, 0, 2, 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