Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79b771e7acdce8d55e24bbf89c52646e0ab835e6bca20f1833c2aec328f52242

Tx prefix hash: 87704ab7d485e0e24ac39cd8c0f9808da2685f8a4ee16723545cbc0e76753a5e
Tx public key: e2cba5063b0e126f6c83f7c687e3b3fa3024696157f7cecdcb89578d995fd9cd
Timestamp: 1730494837 Timestamp [UCT]: 2024-11-01 21:00:37 Age [y:d:h:m:s]: 00:139:09:15:54
Block: 1144486 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99451 RingCT/type: yes/0
Extra: 01e2cba5063b0e126f6c83f7c687e3b3fa3024696157f7cecdcb89578d995fd9cd021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8ceb8a863723700f48c034b4edb0375d94ab21e4af2f819fc94018460a76cb1e 0.600000000000 1628713 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": 1144496, "vin": [ { "gen": { "height": 1144486 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ceb8a863723700f48c034b4edb0375d94ab21e4af2f819fc94018460a76cb1e" } } ], "extra": [ 1, 226, 203, 165, 6, 59, 14, 18, 111, 108, 131, 247, 198, 135, 227, 179, 250, 48, 36, 105, 97, 87, 247, 206, 205, 203, 137, 87, 141, 153, 95, 217, 205, 2, 17, 0, 0, 0, 7, 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