Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb755bdcf687a90f829872cf84a6e6fc823f02369774b5209a7f6bf9a62cc9e8

Tx prefix hash: 34690fbb7441f2740f19fbe5aaef3a22f8e86a4f27bdef1737a2495a01531ff0
Tx public key: b02b7e2b058e23b6e278f29a79c4129ae9121bae3a9113674210a42f3c5fa9ed
Timestamp: 1750541332 Timestamp [UCT]: 2025-06-21 21:28:52 Age [y:d:h:m:s]: 00:153:02:02:51
Block: 1310017 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107263 RingCT/type: yes/0
Extra: 01b02b7e2b058e23b6e278f29a79c4129ae9121bae3a9113674210a42f3c5fa9ed02110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9854692a357e012bb2a0cf7fc2691bab74babf7db49141013659f69a92a954f1 0.600000000000 1797634 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": 1310027, "vin": [ { "gen": { "height": 1310017 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9854692a357e012bb2a0cf7fc2691bab74babf7db49141013659f69a92a954f1" } } ], "extra": [ 1, 176, 43, 126, 43, 5, 142, 35, 182, 226, 120, 242, 154, 121, 196, 18, 154, 233, 18, 27, 174, 58, 145, 19, 103, 66, 16, 164, 47, 60, 95, 169, 237, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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