Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: edfc5c93b421b7132adaf647f46eba02e83f7c2c95917a77c123985c50560c58

Tx prefix hash: a546cd5271b3d7821fb083042d4f5662bfa80b977a45ea20f4d80e5d7c2eaaae
Tx public key: 7c4ee11f4348147cce04e55d3c73c64fa5b0fbed907cced2b1f7f21c855a7ce7
Timestamp: 1726413063 Timestamp [UCT]: 2024-09-15 15:11:03 Age [y:d:h:m:s]: 00:242:09:32:43
Block: 1110727 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173086 RingCT/type: yes/0
Extra: 017c4ee11f4348147cce04e55d3c73c64fa5b0fbed907cced2b1f7f21c855a7ce7021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66176cf520c16f14c6b18e60017e3045344d0f4c5fa02d38f73faac365f6460c 0.600000000000 1589436 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": 1110737, "vin": [ { "gen": { "height": 1110727 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66176cf520c16f14c6b18e60017e3045344d0f4c5fa02d38f73faac365f6460c" } } ], "extra": [ 1, 124, 78, 225, 31, 67, 72, 20, 124, 206, 4, 229, 93, 60, 115, 198, 79, 165, 176, 251, 237, 144, 124, 206, 210, 177, 247, 242, 28, 133, 90, 124, 231, 2, 17, 0, 0, 0, 5, 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