Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 315d24a5ff1729e34666c4466d5dab4ff18b09ebdac60a957dec57d03626e031

Tx prefix hash: bbf7f7d5bac183c6ecdde7bed6eb91f2a609816d5bf357e32167b69fd57ee5df
Tx public key: 32ef5f8b36b0e7a26e9f55d369d74412119644166bde21d1f43b5f35e9b8551c
Timestamp: 1710158922 Timestamp [UCT]: 2024-03-11 12:08:42 Age [y:d:h:m:s]: 01:239:22:28:07
Block: 975984 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 430153 RingCT/type: yes/0
Extra: 0132ef5f8b36b0e7a26e9f55d369d74412119644166bde21d1f43b5f35e9b8551c02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0f09e55a9ec73ec7df718c09d5454b562ba9f27aa7ed5a86659876bf95ded5b 0.600000000000 1435963 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": 975994, "vin": [ { "gen": { "height": 975984 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0f09e55a9ec73ec7df718c09d5454b562ba9f27aa7ed5a86659876bf95ded5b" } } ], "extra": [ 1, 50, 239, 95, 139, 54, 176, 231, 162, 110, 159, 85, 211, 105, 215, 68, 18, 17, 150, 68, 22, 107, 222, 33, 209, 244, 59, 95, 53, 233, 184, 85, 28, 2, 17, 0, 0, 0, 3, 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