Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80339b5d9eb48b6597eb177855b2c55bc16033611f66cf69296ca9db9b5e0d66

Tx prefix hash: a99ff2e053a36a3f59ee5a1e0519241e2d9a6fbbc8471562fc9e4416315412a0
Tx public key: ce64ea947062f8f0116be23f2aeb4905cdc3680ba72e397c8e3dbd87438f374b
Timestamp: 1734428248 Timestamp [UCT]: 2024-12-17 09:37:28 Age [y:d:h:m:s]: 00:098:11:44:59
Block: 1177080 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70154 RingCT/type: yes/0
Extra: 01ce64ea947062f8f0116be23f2aeb4905cdc3680ba72e397c8e3dbd87438f374b0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 997cdd4c04ee75ca4b623fc7e31aa51aa17cd85a0b72cd24c16560e0bf5135a3 0.600000000000 1663443 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": 1177090, "vin": [ { "gen": { "height": 1177080 } } ], "vout": [ { "amount": 600000000, "target": { "key": "997cdd4c04ee75ca4b623fc7e31aa51aa17cd85a0b72cd24c16560e0bf5135a3" } } ], "extra": [ 1, 206, 100, 234, 148, 112, 98, 248, 240, 17, 107, 226, 63, 42, 235, 73, 5, 205, 195, 104, 11, 167, 46, 57, 124, 142, 61, 189, 135, 67, 143, 55, 75, 2, 17, 0, 0, 0, 5, 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