Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3eb2f3bd99b76efb77258ebe76131eb69a3dcfcad4030c702e5e0ecf020eb7c0

Tx prefix hash: adc65e4058f37847371de16ff250f046e28deda16d71ad5aee24cc609bc7ea7b
Tx public key: c944a81f191a63c4e2422a17a7d5fad1c10b316e6464bac286d6ffb82f956848
Timestamp: 1726490639 Timestamp [UCT]: 2024-09-16 12:43:59 Age [y:d:h:m:s]: 00:181:23:43:18
Block: 1111367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129902 RingCT/type: yes/0
Extra: 01c944a81f191a63c4e2422a17a7d5fad1c10b316e6464bac286d6ffb82f956848021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0d856dbcad083b5096751c5f31db56491e0a974fd34c2e4f912e6d6f21fd456 0.600000000000 1590298 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": 1111377, "vin": [ { "gen": { "height": 1111367 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0d856dbcad083b5096751c5f31db56491e0a974fd34c2e4f912e6d6f21fd456" } } ], "extra": [ 1, 201, 68, 168, 31, 25, 26, 99, 196, 226, 66, 42, 23, 167, 213, 250, 209, 193, 11, 49, 110, 100, 100, 186, 194, 134, 214, 255, 184, 47, 149, 104, 72, 2, 17, 0, 0, 0, 2, 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