Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71d9f693824888b882816ee95c8e7e1f2de5e56105fe38484d199eef553b2a52

Tx prefix hash: 4c70e1205671be9a60d151593efaa1d23d2d609343da971461fd37f8a5d6b507
Tx public key: ea1b9ce52cfca114fbe38542dc8e6dc20e5b884520044c16a53266f2dcaa60c7
Timestamp: 1718196706 Timestamp [UCT]: 2024-06-12 12:51:46 Age [y:d:h:m:s]: 00:343:13:26:40
Block: 1042614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245561 RingCT/type: yes/0
Extra: 01ea1b9ce52cfca114fbe38542dc8e6dc20e5b884520044c16a53266f2dcaa60c70211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3b41c98d08691804a0775c0235b2f9c4499f1d9fc8faa87ebe18e32595a2a69 0.600000000000 1511569 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": 1042624, "vin": [ { "gen": { "height": 1042614 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3b41c98d08691804a0775c0235b2f9c4499f1d9fc8faa87ebe18e32595a2a69" } } ], "extra": [ 1, 234, 27, 156, 229, 44, 252, 161, 20, 251, 227, 133, 66, 220, 142, 109, 194, 14, 91, 136, 69, 32, 4, 76, 22, 165, 50, 102, 242, 220, 170, 96, 199, 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