Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8d4893a5dd70d5e000a00bc1f263869c1aab6bcbe7e354283bc765591ee40cb

Tx prefix hash: d1281449d0ad671f2dacb033a5e8f266fe7ad0b6ef0ae6c9f67239700dea4c03
Tx public key: 79da35a6b5a858d1ca417668a4d9bf15e438a8ff2ea4cdd6cc6e1b011b78d819
Timestamp: 1734755457 Timestamp [UCT]: 2024-12-21 04:30:57 Age [y:d:h:m:s]: 00:096:10:29:48
Block: 1179793 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68674 RingCT/type: yes/0
Extra: 0179da35a6b5a858d1ca417668a4d9bf15e438a8ff2ea4cdd6cc6e1b011b78d8190211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3380054eee1d98f30fea97bd0e3964fd2d2deff1d7c4b8103991ef86abe4afa0 0.600000000000 1666192 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": 1179803, "vin": [ { "gen": { "height": 1179793 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3380054eee1d98f30fea97bd0e3964fd2d2deff1d7c4b8103991ef86abe4afa0" } } ], "extra": [ 1, 121, 218, 53, 166, 181, 168, 88, 209, 202, 65, 118, 104, 164, 217, 191, 21, 228, 56, 168, 255, 46, 164, 205, 214, 204, 110, 27, 1, 27, 120, 216, 25, 2, 17, 0, 0, 0, 3, 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