Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4978a7828c91115959dc62ef1a6196d96fdd4021cfded92bd43778d9215e9352

Tx prefix hash: 648c2f8d2c3c817a68f91be0cdd03942d4287f84c333dc54054dbacb6732380b
Tx public key: f0c5ef95dcf30088d3b50c9df238ee2ce03a0013eff3a99b4c3c8a15042235b3
Timestamp: 1705652357 Timestamp [UCT]: 2024-01-19 08:19:17 Age [y:d:h:m:s]: 01:090:12:54:20
Block: 938582 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325825 RingCT/type: yes/0
Extra: 01f0c5ef95dcf30088d3b50c9df238ee2ce03a0013eff3a99b4c3c8a15042235b30211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e9da5f84cfd20c76c2bb663bd961e862428f0c22c58a5350c0696114929dddd 0.600000000000 1396652 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": 938592, "vin": [ { "gen": { "height": 938582 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e9da5f84cfd20c76c2bb663bd961e862428f0c22c58a5350c0696114929dddd" } } ], "extra": [ 1, 240, 197, 239, 149, 220, 243, 0, 136, 211, 181, 12, 157, 242, 56, 238, 44, 224, 58, 0, 19, 239, 243, 169, 155, 76, 60, 138, 21, 4, 34, 53, 179, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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