Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe2e87cf36da0baefc14c0bafd3c77a4132809d6412678d3e931f65aa8e3a41d

Tx prefix hash: 11fdb6f8220abb18ddc47532f3ffe299d18a92cf2806147fef47fc1b0fa73074
Tx public key: 07196da7924fdc7f92f941b08f954735c51f33f17be7a52cab72b3abaf19b94d
Timestamp: 1756091654 Timestamp [UCT]: 2025-08-25 03:14:14 Age [y:d:h:m:s]: 00:127:05:22:49
Block: 1353850 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90920 RingCT/type: yes/0
Extra: 0107196da7924fdc7f92f941b08f954735c51f33f17be7a52cab72b3abaf19b94d0211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b769c5663b4b934f3774688611c0acd795f2008a8a3d553eb231149294aec70d 0.600000000000 1841829 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": 1353860, "vin": [ { "gen": { "height": 1353850 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b769c5663b4b934f3774688611c0acd795f2008a8a3d553eb231149294aec70d" } } ], "extra": [ 1, 7, 25, 109, 167, 146, 79, 220, 127, 146, 249, 65, 176, 143, 149, 71, 53, 197, 31, 51, 241, 123, 231, 165, 44, 171, 114, 179, 171, 175, 25, 185, 77, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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