Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f81f2370f894bc16d5ac2f81b12c8dbd37d1abc3d5724543e9d7bc203cecbf1c

Tx prefix hash: 6b1f0ffd27ec6b417a9f15badc0de74d718c3a48098bd602fe69396f1c4fb5dc
Tx public key: 0e31e88d4348793ecd7661570aa44e121656b867f5b73cd30ff75668d4ce4453
Timestamp: 1715194044 Timestamp [UCT]: 2024-05-08 18:47:24 Age [y:d:h:m:s]: 00:349:11:40:06
Block: 1017726 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249798 RingCT/type: yes/0
Extra: 010e31e88d4348793ecd7661570aa44e121656b867f5b73cd30ff75668d4ce44530211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c063d480eb432b8e4183939bea6949619e4396d11a6ce8abae00afae2bf5d8b 0.600000000000 1481511 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": 1017736, "vin": [ { "gen": { "height": 1017726 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c063d480eb432b8e4183939bea6949619e4396d11a6ce8abae00afae2bf5d8b" } } ], "extra": [ 1, 14, 49, 232, 141, 67, 72, 121, 62, 205, 118, 97, 87, 10, 164, 78, 18, 22, 86, 184, 103, 245, 183, 60, 211, 15, 247, 86, 104, 212, 206, 68, 83, 2, 17, 0, 0, 0, 4, 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