Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c90a0ca6f21fdbeabd9355794de9eda77bd60b6887e9f45476b048909f0dadc

Tx prefix hash: b59f67f07d91edff74c35a2849139cc822ceb90b1bf62571c1a35fdfc8b50e24
Tx public key: f8ccb908135ce8ef10624254fd0c6d6303bf7cc91d02668a8978a012b0b9e7a3
Timestamp: 1748131002 Timestamp [UCT]: 2025-05-24 23:56:42 Age [y:d:h:m:s]: 00:180:16:22:55
Block: 1290244 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126816 RingCT/type: yes/0
Extra: 01f8ccb908135ce8ef10624254fd0c6d6303bf7cc91d02668a8978a012b0b9e7a3021100000004a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b62ac16e1d2481bcc8cf8674980340a900dbdfe61716979f3e0b4a22ad89702e 0.600000000000 1777713 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": 1290254, "vin": [ { "gen": { "height": 1290244 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b62ac16e1d2481bcc8cf8674980340a900dbdfe61716979f3e0b4a22ad89702e" } } ], "extra": [ 1, 248, 204, 185, 8, 19, 92, 232, 239, 16, 98, 66, 84, 253, 12, 109, 99, 3, 191, 124, 201, 29, 2, 102, 138, 137, 120, 160, 18, 176, 185, 231, 163, 2, 17, 0, 0, 0, 4, 161, 29, 186, 152, 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