Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c7aedd2a22238ddf54ee5670fd95bcd8e5a9d550933c001a946a2d60a169543

Tx prefix hash: 933dadb5ba82dbda7066c24445b134717894edaa3e60fcd0ce446a1c4e7472af
Tx public key: 507f051d0defc158547ca98664b0ac1af9c836b8d6a4369a46a161a6ed5bf36d
Timestamp: 1750519784 Timestamp [UCT]: 2025-06-21 15:29:44 Age [y:d:h:m:s]: 00:152:19:02:54
Block: 1309838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107051 RingCT/type: yes/0
Extra: 01507f051d0defc158547ca98664b0ac1af9c836b8d6a4369a46a161a6ed5bf36d02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4c79f888a054113ad2499b079c66a6c1cf8da840bc9e97b85f7a90e7e9e8de8 0.600000000000 1797455 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": 1309848, "vin": [ { "gen": { "height": 1309838 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4c79f888a054113ad2499b079c66a6c1cf8da840bc9e97b85f7a90e7e9e8de8" } } ], "extra": [ 1, 80, 127, 5, 29, 13, 239, 193, 88, 84, 124, 169, 134, 100, 176, 172, 26, 249, 200, 54, 184, 214, 164, 54, 154, 70, 161, 97, 166, 237, 91, 243, 109, 2, 17, 0, 0, 0, 1, 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