Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd6a80d4162a2ce1de7af804b7e660fce3408aff27f4774c59ae4d29c9a52b10

Tx prefix hash: 2690942bc9e1ba86948579cef7134a5d4aa0758a587c60e931fb7f1244dedfc4
Tx public key: bb70a266e3934c2dd0b8061b8be5ea25df99aad5e141b664815ce0dcf349edb1
Timestamp: 1740944079 Timestamp [UCT]: 2025-03-02 19:34:39 Age [y:d:h:m:s]: 00:257:22:15:34
Block: 1230726 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182087 RingCT/type: yes/0
Extra: 01bb70a266e3934c2dd0b8061b8be5ea25df99aad5e141b664815ce0dcf349edb10211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07ad3099edbf0de6db07bcafb21a8e80c9f853a386d40b3668706ac41e8bb3be 0.600000000000 1717625 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": 1230736, "vin": [ { "gen": { "height": 1230726 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07ad3099edbf0de6db07bcafb21a8e80c9f853a386d40b3668706ac41e8bb3be" } } ], "extra": [ 1, 187, 112, 162, 102, 227, 147, 76, 45, 208, 184, 6, 27, 139, 229, 234, 37, 223, 153, 170, 213, 225, 65, 182, 100, 129, 92, 224, 220, 243, 73, 237, 177, 2, 17, 0, 0, 0, 9, 31, 10, 83, 235, 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