Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c09f2e5f4a574b9745844f32d5e7d41a1d696881b58bdaadeb9340010266fca2

Tx prefix hash: f7cbcd8884b1596fbf2a4bc27feee06fac66cb374813e8996b0aec3f98c4316c
Tx public key: 3e8c3ba3d97491c2a3d76f94bcf628002a401fde1b31cafa342e50cebb369097
Timestamp: 1750553928 Timestamp [UCT]: 2025-06-22 00:58:48 Age [y:d:h:m:s]: 00:152:18:06:10
Block: 1310114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107034 RingCT/type: yes/0
Extra: 013e8c3ba3d97491c2a3d76f94bcf628002a401fde1b31cafa342e50cebb369097021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91ac56f052dd454b31e701e6c0c01598e3eca421fef896dd0c2f9139961fcb74 0.600000000000 1797731 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": 1310124, "vin": [ { "gen": { "height": 1310114 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91ac56f052dd454b31e701e6c0c01598e3eca421fef896dd0c2f9139961fcb74" } } ], "extra": [ 1, 62, 140, 59, 163, 217, 116, 145, 194, 163, 215, 111, 148, 188, 246, 40, 0, 42, 64, 31, 222, 27, 49, 202, 250, 52, 46, 80, 206, 187, 54, 144, 151, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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