Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cdc6877181c0a3939ddea05b1d8341de9d3debe1664388fcd2446cba0a92bb67

Tx prefix hash: b230f72807334d7dd51d196208e2732da22324f03d5918bb39972864d4001565
Tx public key: 630b9c6fe3f5735f944f8b50f3a3a15bf4e4c01ba9bc9b31e0bc7042e4ad3c05
Timestamp: 1745594164 Timestamp [UCT]: 2025-04-25 15:16:04 Age [y:d:h:m:s]: 00:206:18:03:00
Block: 1269229 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145485 RingCT/type: yes/0
Extra: 01630b9c6fe3f5735f944f8b50f3a3a15bf4e4c01ba9bc9b31e0bc7042e4ad3c050211000000016c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3299cefd5c502ae1482c0532552b129d3232d40336c6f7553b043264eb33c8fc 0.600000000000 1756464 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": 1269239, "vin": [ { "gen": { "height": 1269229 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3299cefd5c502ae1482c0532552b129d3232d40336c6f7553b043264eb33c8fc" } } ], "extra": [ 1, 99, 11, 156, 111, 227, 245, 115, 95, 148, 79, 139, 80, 243, 163, 161, 91, 244, 228, 192, 27, 169, 188, 155, 49, 224, 188, 112, 66, 228, 173, 60, 5, 2, 17, 0, 0, 0, 1, 108, 152, 170, 61, 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