Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b11090b685a3b15ae9dcfb71f65ab32afa5ccf1df55d570fcd5e850c1289609

Tx prefix hash: 344ecec3b7b002d5448dfb7e5dc0ed25aa5cd43f7343844ea8111f62f21e1ebd
Tx public key: 97de30656626b05a7b4e85f83be1f9cbb233f53191115bd7cce0de82f816e6e5
Timestamp: 1736415273 Timestamp [UCT]: 2025-01-09 09:34:33 Age [y:d:h:m:s]: 00:315:12:45:26
Block: 1193502 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223027 RingCT/type: yes/0
Extra: 0197de30656626b05a7b4e85f83be1f9cbb233f53191115bd7cce0de82f816e6e50211000000101f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f2c8eb61019ac4533ef433a2e3a45de4053858a247ab3a63b02dcc2b0743a4a 0.600000000000 1680063 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": 1193512, "vin": [ { "gen": { "height": 1193502 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f2c8eb61019ac4533ef433a2e3a45de4053858a247ab3a63b02dcc2b0743a4a" } } ], "extra": [ 1, 151, 222, 48, 101, 102, 38, 176, 90, 123, 78, 133, 248, 59, 225, 249, 203, 178, 51, 245, 49, 145, 17, 91, 215, 204, 224, 222, 130, 248, 22, 230, 229, 2, 17, 0, 0, 0, 16, 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