Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05aca0322c0d67dc3bf5018fd67cb86868b4b01b96cfa602ff0355ddd25bfcc0

Tx prefix hash: 2e49fe795463dc140874a55f643dd9948b022cf61850d42592c162cd47574958
Tx public key: 04f0419e7ba86eb594dfe938e83780ac6dcbb87b1a958e2b0b45089d82c6e1f3
Timestamp: 1751454226 Timestamp [UCT]: 2025-07-02 11:03:46 Age [y:d:h:m:s]: 00:130:11:01:29
Block: 1317179 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91478 RingCT/type: yes/0
Extra: 0104f0419e7ba86eb594dfe938e83780ac6dcbb87b1a958e2b0b45089d82c6e1f3021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ad9ce40445a14da3745ced2d26228703652bb7abf84e715dcf10c5867e4ed4a 0.600000000000 1804844 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": 1317189, "vin": [ { "gen": { "height": 1317179 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ad9ce40445a14da3745ced2d26228703652bb7abf84e715dcf10c5867e4ed4a" } } ], "extra": [ 1, 4, 240, 65, 158, 123, 168, 110, 181, 148, 223, 233, 56, 232, 55, 128, 172, 109, 203, 184, 123, 26, 149, 142, 43, 11, 69, 8, 157, 130, 198, 225, 243, 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