Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c90f4933d9af676384638e94ed07c8771f2e8368c549d19cdd1f28172079e85c

Tx prefix hash: 4a1f4c290defc9c0ff6b54d69d931f07f685bbba0c53b1036f7950269cd4e652
Tx public key: b4d68204a8e3a9aea783d2acce16cea23119a9bae0851fde5bd13a21a973af21
Timestamp: 1728445048 Timestamp [UCT]: 2024-10-09 03:37:28 Age [y:d:h:m:s]: 00:215:11:47:59
Block: 1127569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153816 RingCT/type: yes/0
Extra: 01b4d68204a8e3a9aea783d2acce16cea23119a9bae0851fde5bd13a21a973af2102110000000d91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bea5c2a1fe634454b28d7b3125f1b675998086dc02cdc81dc7eba78a6b4d8a6e 0.600000000000 1610376 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": 1127579, "vin": [ { "gen": { "height": 1127569 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bea5c2a1fe634454b28d7b3125f1b675998086dc02cdc81dc7eba78a6b4d8a6e" } } ], "extra": [ 1, 180, 214, 130, 4, 168, 227, 169, 174, 167, 131, 210, 172, 206, 22, 206, 162, 49, 25, 169, 186, 224, 133, 31, 222, 91, 209, 58, 33, 169, 115, 175, 33, 2, 17, 0, 0, 0, 13, 145, 225, 60, 4, 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