Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc60ab004686fd01ea93f232ee31ca9fa23a8758dccfd073c824d043df761668

Tx prefix hash: d6b851a3652876c5f8308b23424e1f3e93305b52ec017b0c9690d1b159cb8acb
Tx public key: 27c1b7e63938fa5003c7ce904d7c6617f8aef6d926d63273f5d25d91358180c4
Timestamp: 1715359117 Timestamp [UCT]: 2024-05-10 16:38:37 Age [y:d:h:m:s]: 00:328:14:09:22
Block: 1019079 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234878 RingCT/type: yes/0
Extra: 0127c1b7e63938fa5003c7ce904d7c6617f8aef6d926d63273f5d25d91358180c402110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2cb8d84ed55f3fed19a7dcf3501a69bee6bd8a538471adbab69be6dadd047072 0.600000000000 1482952 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": 1019089, "vin": [ { "gen": { "height": 1019079 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2cb8d84ed55f3fed19a7dcf3501a69bee6bd8a538471adbab69be6dadd047072" } } ], "extra": [ 1, 39, 193, 183, 230, 57, 56, 250, 80, 3, 199, 206, 144, 77, 124, 102, 23, 248, 174, 246, 217, 38, 214, 50, 115, 245, 210, 93, 145, 53, 129, 128, 196, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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