Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b0d6e69e4cd7ed6a1cf091a89cc532628e91ac8ed0f7464259ae224f92b4acd

Tx prefix hash: 937fd8b9a48cfde92df5a8285b04739500c1696954888de7298d8c0428e958ce
Tx public key: 2133875d325d19c12fbda303bcfe571c1b9ef72454e368d5b179d82e71e94fc1
Timestamp: 1726394600 Timestamp [UCT]: 2024-09-15 10:03:20 Age [y:d:h:m:s]: 00:207:02:06:28
Block: 1110566 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147843 RingCT/type: yes/0
Extra: 012133875d325d19c12fbda303bcfe571c1b9ef72454e368d5b179d82e71e94fc1021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b0fb2b9ebcdef9cc58273a4be349caf681dfbcae773a5cf8ca2305b2e707ca6 0.600000000000 1589217 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": 1110576, "vin": [ { "gen": { "height": 1110566 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b0fb2b9ebcdef9cc58273a4be349caf681dfbcae773a5cf8ca2305b2e707ca6" } } ], "extra": [ 1, 33, 51, 135, 93, 50, 93, 25, 193, 47, 189, 163, 3, 188, 254, 87, 28, 27, 158, 247, 36, 84, 227, 104, 213, 177, 121, 216, 46, 113, 233, 79, 193, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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