Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8504fd7a351aec490cd73011d112b219049a23288328cf85a44e7e919bedece

Tx prefix hash: f9350d31b7321f9d890670c2c61ffbc1cc966933ff2471362a8b532f905ef574
Tx public key: c5f89f78e36c0813f1ff63806f6c92c1a1a194d9eee5f0249febcca2b00b38e0
Timestamp: 1704174725 Timestamp [UCT]: 2024-01-02 05:52:05 Age [y:d:h:m:s]: 01:131:08:17:44
Block: 926347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355009 RingCT/type: yes/0
Extra: 01c5f89f78e36c0813f1ff63806f6c92c1a1a194d9eee5f0249febcca2b00b38e00211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30814f36d636e55b8f3558fb3b6b70b9374d858110ca58b189d1130fbed7eee6 0.600000000000 1384129 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": 926357, "vin": [ { "gen": { "height": 926347 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30814f36d636e55b8f3558fb3b6b70b9374d858110ca58b189d1130fbed7eee6" } } ], "extra": [ 1, 197, 248, 159, 120, 227, 108, 8, 19, 241, 255, 99, 128, 111, 108, 146, 193, 161, 161, 148, 217, 238, 229, 240, 36, 159, 235, 204, 162, 176, 11, 56, 224, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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