Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd6fb01e56503e000bd9847f134413ca52838b1a833f24cb176587e8a3f50a25

Tx prefix hash: 34807497f3c161656bd213ba30145b2b48d8521129006563b1807f7b91eaec18
Tx public key: c90d9e1ca7f0125cfbca2b88ec829ba1915e2fab59ad3f45051e6e18b696d231
Timestamp: 1705013729 Timestamp [UCT]: 2024-01-11 22:55:29 Age [y:d:h:m:s]: 01:085:11:06:13
Block: 933297 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322190 RingCT/type: yes/0
Extra: 01c90d9e1ca7f0125cfbca2b88ec829ba1915e2fab59ad3f45051e6e18b696d23102110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1d6c194dd383b9579b77455ff09ec203f7097dc6d3c569f8e187a1486fc2a3e 0.600000000000 1391259 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": 933307, "vin": [ { "gen": { "height": 933297 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1d6c194dd383b9579b77455ff09ec203f7097dc6d3c569f8e187a1486fc2a3e" } } ], "extra": [ 1, 201, 13, 158, 28, 167, 240, 18, 92, 251, 202, 43, 136, 236, 130, 155, 161, 145, 94, 47, 171, 89, 173, 63, 69, 5, 30, 110, 24, 182, 150, 210, 49, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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