Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 092e056251d8b9c35371bad23c6b361a521498e877b9a0ab5cd86e90640854b0

Tx prefix hash: 8274257966398b807dcd7169f5cd1c7f635813f3210364d905553333d78253ef
Tx public key: 62e1c33e2f088b5432c95d62240017b9f7d21a13ddc3640f95b8538c866f7b4d
Timestamp: 1727775391 Timestamp [UCT]: 2024-10-01 09:36:31 Age [y:d:h:m:s]: 00:236:03:43:08
Block: 1122021 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168624 RingCT/type: yes/0
Extra: 0162e1c33e2f088b5432c95d62240017b9f7d21a13ddc3640f95b8538c866f7b4d021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ba5e5cca88ae44a797504df150d56439718c0e5a36d34ce5c5fdd302f1738c0 0.600000000000 1604386 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": 1122031, "vin": [ { "gen": { "height": 1122021 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ba5e5cca88ae44a797504df150d56439718c0e5a36d34ce5c5fdd302f1738c0" } } ], "extra": [ 1, 98, 225, 195, 62, 47, 8, 139, 84, 50, 201, 93, 98, 36, 0, 23, 185, 247, 210, 26, 19, 221, 195, 100, 15, 149, 184, 83, 140, 134, 111, 123, 77, 2, 17, 0, 0, 0, 4, 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