Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06196f2cf88dc5dfe1796a7350e7f7532cb43d265e071ca725d2e1232063aee8

Tx prefix hash: c010bea1aa321eb7ad4b29464ebd0d1ec48f031f3a66f3fe06b36ae26dd820f2
Tx public key: 742a8469897cbe3063da2473d48afd68bb8c40fb30ba1bd88a65add62a40a144
Timestamp: 1725065550 Timestamp [UCT]: 2024-08-31 00:52:30 Age [y:d:h:m:s]: 00:258:19:40:40
Block: 1099552 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184855 RingCT/type: yes/0
Extra: 01742a8469897cbe3063da2473d48afd68bb8c40fb30ba1bd88a65add62a40a144021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ff5cae7ac1c18d0cf6e928b0413e1c5ff8a30effbd287bfe4faf0c64325d166 0.600000000000 1575515 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": 1099562, "vin": [ { "gen": { "height": 1099552 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ff5cae7ac1c18d0cf6e928b0413e1c5ff8a30effbd287bfe4faf0c64325d166" } } ], "extra": [ 1, 116, 42, 132, 105, 137, 124, 190, 48, 99, 218, 36, 115, 212, 138, 253, 104, 187, 140, 64, 251, 48, 186, 27, 216, 138, 101, 173, 214, 42, 64, 161, 68, 2, 17, 0, 0, 0, 6, 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