Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c615735ca058edaeee4762fbf6316f59b91e858f0916f0a5da230948e20e05b2

Tx prefix hash: b0ad843042a8d1252dfdd80f2be2a57cf17a328ca5cd4e75ac385cc91b696ff5
Tx public key: 0015f1e7c6915c8e181fa211f80fb1b51f890053a950a3c051cc776df8ed0802
Timestamp: 1754453828 Timestamp [UCT]: 2025-08-06 04:17:08 Age [y:d:h:m:s]: 00:013:15:36:30
Block: 1341236 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8850 RingCT/type: yes/0
Extra: 010015f1e7c6915c8e181fa211f80fb1b51f890053a950a3c051cc776df8ed0802021100000003b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1058d87890bb4d65ac572210583596574f2321c6f5ef874495c58f119ab324c 0.600000000000 1829059 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": 1341246, "vin": [ { "gen": { "height": 1341236 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1058d87890bb4d65ac572210583596574f2321c6f5ef874495c58f119ab324c" } } ], "extra": [ 1, 0, 21, 241, 231, 198, 145, 92, 142, 24, 31, 162, 17, 248, 15, 177, 181, 31, 137, 0, 83, 169, 80, 163, 192, 81, 204, 119, 109, 248, 237, 8, 2, 2, 17, 0, 0, 0, 3, 178, 247, 132, 196, 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