Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c670b3f1e0a4d82002cc01f683e62559520b9e570ab6a5082e6bb0d3a2f205e

Tx prefix hash: c07ad2ac08376da595b93f1698e77e5f74887d29befe77ca5ee907288aa07148
Tx public key: 38532c5ed54a46f35e5553c538da85a1df7473d215c9608e757e9831ca6e4e78
Timestamp: 1722379608 Timestamp [UCT]: 2024-07-30 22:46:48 Age [y:d:h:m:s]: 00:278:00:48:44
Block: 1077281 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198631 RingCT/type: yes/0
Extra: 0138532c5ed54a46f35e5553c538da85a1df7473d215c9608e757e9831ca6e4e7802110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 177b9c276ae49fbef6afbf9b3e41f9f5721d592d46116ea1aa470696b04af7d2 0.600000000000 1549828 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": 1077291, "vin": [ { "gen": { "height": 1077281 } } ], "vout": [ { "amount": 600000000, "target": { "key": "177b9c276ae49fbef6afbf9b3e41f9f5721d592d46116ea1aa470696b04af7d2" } } ], "extra": [ 1, 56, 83, 44, 94, 213, 74, 70, 243, 94, 85, 83, 197, 56, 218, 133, 161, 223, 116, 115, 210, 21, 201, 96, 142, 117, 126, 152, 49, 202, 110, 78, 120, 2, 17, 0, 0, 0, 12, 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