Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a32cd1fc9d1f8f95250a097741d9a88d4d5a58d1613df3939c15c7ec9bc9bff

Tx prefix hash: 27462470dd5102d614d88364655081f81c253c3711bce8971570b177f75a40d9
Tx public key: 152d40d375ddb8c3889b8b3b766691724edf714242384a7e53d311d4baff92c6
Timestamp: 1745888892 Timestamp [UCT]: 2025-04-29 01:08:12 Age [y:d:h:m:s]: 00:255:16:15:34
Block: 1271674 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180518 RingCT/type: yes/0
Extra: 01152d40d375ddb8c3889b8b3b766691724edf714242384a7e53d311d4baff92c60211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ddd67ccf4decfa9b731df5b3805dc7c52904ad3b8955ff42831f9fce0106f78a 0.600000000000 1758941 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": 1271684, "vin": [ { "gen": { "height": 1271674 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ddd67ccf4decfa9b731df5b3805dc7c52904ad3b8955ff42831f9fce0106f78a" } } ], "extra": [ 1, 21, 45, 64, 211, 117, 221, 184, 195, 136, 155, 139, 59, 118, 102, 145, 114, 78, 223, 113, 66, 66, 56, 74, 126, 83, 211, 17, 212, 186, 255, 146, 198, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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