Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22c049f76648151f03b7c1d2a1453d2a289c629369f9c95f86e8bf11fa862837

Tx prefix hash: 6d38bdf612e2f1c9cf99568dea7e3c255398355b3e635c67696bcb3b6357d088
Tx public key: 9131e989098d0dd562319b7b0444ac1f7fa688e7d98dfecc011a66b3b614931f
Timestamp: 1710398875 Timestamp [UCT]: 2024-03-14 06:47:55 Age [y:d:h:m:s]: 01:011:09:32:51
Block: 977975 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 269111 RingCT/type: yes/0
Extra: 019131e989098d0dd562319b7b0444ac1f7fa688e7d98dfecc011a66b3b614931f02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ed49e7851ae36beb4be79fcdf78b076454e60ca053b5240e04e4890e7fb40af9 0.600000000000 1437984 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": 977985, "vin": [ { "gen": { "height": 977975 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed49e7851ae36beb4be79fcdf78b076454e60ca053b5240e04e4890e7fb40af9" } } ], "extra": [ 1, 145, 49, 233, 137, 9, 141, 13, 213, 98, 49, 155, 123, 4, 68, 172, 31, 127, 166, 136, 231, 217, 141, 254, 204, 1, 26, 102, 179, 182, 20, 147, 31, 2, 17, 0, 0, 0, 1, 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