Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ee16c7b06330e61c3b7bffca1d78187eb4d9b596d311bcfa70a0748198ecec4

Tx prefix hash: b9424df614081169f49084cf74d45514907eaa0e14dd8d2b391c3f9e36528881
Tx public key: febf04722f2670ac0f50a8ba35f8b1e2b705f84b4722eeeebffd6a951ec2b098
Timestamp: 1734192298 Timestamp [UCT]: 2024-12-14 16:04:58 Age [y:d:h:m:s]: 00:118:10:37:05
Block: 1175122 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84435 RingCT/type: yes/0
Extra: 01febf04722f2670ac0f50a8ba35f8b1e2b705f84b4722eeeebffd6a951ec2b098021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41fe92bd4dbfb74a1473069e4efd922254f4bf3b7f2c13352c7d752f378e9fb1 0.600000000000 1661359 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": 1175132, "vin": [ { "gen": { "height": 1175122 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41fe92bd4dbfb74a1473069e4efd922254f4bf3b7f2c13352c7d752f378e9fb1" } } ], "extra": [ 1, 254, 191, 4, 114, 47, 38, 112, 172, 15, 80, 168, 186, 53, 248, 177, 226, 183, 5, 248, 75, 71, 34, 238, 238, 191, 253, 106, 149, 30, 194, 176, 152, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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