Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffa626129c8a513f6eed9612007f0d4fd12b29baefed3a43384c7be54cfa31b6

Tx prefix hash: 08d61ec31d7f57562e99a8208065797e8fa81680953e65bdfa21a0d471f04edd
Tx public key: 3c7d50273ba87b67803e839238f33729d345ab545dd0c61a8a135f7c669835eb
Timestamp: 1713256289 Timestamp [UCT]: 2024-04-16 08:31:29 Age [y:d:h:m:s]: 01:059:10:13:38
Block: 1001630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303388 RingCT/type: yes/0
Extra: 013c7d50273ba87b67803e839238f33729d345ab545dd0c61a8a135f7c669835eb02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aea0812920b0a6c1753d6a2b836a54d01a01ce8b269048c65e9c13e8f1aa58d3 0.600000000000 1462136 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": 1001640, "vin": [ { "gen": { "height": 1001630 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aea0812920b0a6c1753d6a2b836a54d01a01ce8b269048c65e9c13e8f1aa58d3" } } ], "extra": [ 1, 60, 125, 80, 39, 59, 168, 123, 103, 128, 62, 131, 146, 56, 243, 55, 41, 211, 69, 171, 84, 93, 208, 198, 26, 138, 19, 95, 124, 102, 152, 53, 235, 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